--------------------------------------------------------------------------------
PROFINET IO-Controller
--------------------------------------------------------------------------------

V2.7.0.7
--------
 - PSPNM-697:  Occasional crash when connection aborts 


V2.7.0.6
--------
 - PSPNM-695:  Receipt of more than one DCP Signal will lead to situation that LED flashing never stops on rcX 2.1 based systems 


V2.7.0.5
--------
 - PSPNM-693:  possible race condition in statemachine may lead to crash on rcX 2.1 based systems 


V2.7.0.4
--------
 - PSPNM-691:  IP port 80 unexpectedly not available for usage with EthernetInterface 


V2.7.0.3
--------
 - PSPNM-689:  online view in newest version of Topology tool Proneta shown strange characters 
 - PSPNM-690:  update to SNMP V4.4.0.2 and LLDP V4.4.0.1 
 - PSPNM-692:  NXLFW delivery does not contain all required TCP/IP header files 


V2.7.0.2
--------
 - PSPNM-682:  IO Controller never sets its APDU_STATUS.RUN in case of input-only IO Devices 
 - PSPNM-683:  Invalid use of TLR_BOOLEAN in API Header 
 - PSPNM-687:  feature: add possibility to disable the AP task behavior to clear the registered task of a DPM channel 


V2.7.0.1
--------
 - PSPNM-679:  IO Devices reporting diagnosis disappears may be displayed as having diagnosis in bitlists and MasterStatusBlock 


V2.7.0.0
--------
 - PSPNM-660:  setting an IO Device port to a fixed MAUType does not work for some physics 
 - PSPNM-665:  change versionnumber from v2.6 to V2.7 
 - PSPNM-668:  feature: add support for loadable module with rcX v2.1 
 - PSPNM-669:  update to rcX V2.1.11.2 and rcX 2.0.28.0 


V2.6.20.0
---------
 - PSPNM-650:  [loadable module]: cyclic communication not possible 


V2.6.19.0
---------
 - PSPNM-564:  feature: add support to blink with the LEDs when DCP Signal is issued by another station 
 - PSPNM-572:  update to v2.0.8.24 
 - PSPNM-576:  RCX_GET_DPM_IO_INFO_REQ returns unexpected start offset for inputs in case of manual submodule DPM addressing  
 - PSPNM-605:  after multiple download a valid database is rejected with configuration fault 
 - PSPNM-610:  IO Device reporting a substitute submodule ar connection establishment is marked as faulty 
 - PSPNM-613:  after many (>20000) reconfigurations the firmware crashes 


V2.6.18.1
---------
 - PSPNM-650:  [loadable module]: cyclic communication not possible 


V2.6.18.0
---------
 - PSPNM-565:  RPC Server uses wrong UDP source port (certification issue) 


V2.6.17.0
---------
 - PSPNM-563:  RPC EndPointMapper uses wrong UDP port (certification issue) 


V2.6.16.0
---------
 - PSPNM-562:  fragmented Write Requests are not working at all 


V2.6.15.0
---------
 - PSPNM-506:  invalid UDP source port used for acyclic services and connection establishment (certification issue) 
 - PSPNM-507:  alarm to indicate communicaton timeout is sent to late on the bus (certification issue) 
 - PSPNM-560:  IP port range set via taglist is ignored by TCP/IP stack 
 - PSPNM-561:  update to DCERPC V4.0.20.0 


V2.6.14.0
---------
 - PSPNM-505:  [cifX]: DMA not working 


V2.6.13.0
---------
 - PSPNM-504:  invalid sequence number handling in Alarm statemachines 


V2.6.12.1
---------
 - PSPNM-503:  [loadable module]EthernetInterface portrange can not be configured 


V2.6.12.0
---------
 - PSPNM-475:  feature: Add support of Ethernet Interface on second DPM channel 
 - PSPNM-484:  Firmware version used for identification can not be changed when using Sycon.net configuration 


V2.6.11.0
---------
 - PSPNM-482:  ChannelInit sometimes not completed by firmware 


V2.6.10.0
---------
 - PSPNM-474:  No separate configuration of PHY settings for ports 0 and 1 possible 


V2.6.9.3
--------
 - PSPNM-479:  handling of DPM-fragmented Read Records does not work as expected 


V2.6.9.2
--------
 - PSPNM-478:  sometimes no Read confirmation received in application 


V2.6.9.1
--------
 - PSPNM-472:  using PNIO_APCTL_CMD_SET_VERSIONINFO_REQ may produce unexpected version in RPC EPM lookup 
 - PSPNM-473:  after performing about 260 bus state changes (on -> off, off -> on) without requesting io data update the firmware will crash 


V2.6.9.0
--------
 - PSPNM-467:  feature: allow application to set the version numbers used by firmware as identification info for SNMP and RPC 
 - PSPNM-469:  update to new RPC version 4.0.17.0 
 - PSPNM-470:  update to new SNMP version v4.1.4.0 


V2.6.8.1
--------
 - PSPNM-464:  when ChannelInit is executed shortly after PNIO_APCTL_CMD_RELEASE_REQ was used firmware is locked 
 - PSPNM-466:  if IO-Device is disconnected and reconnected the IO-Data in DPM is not updated at first DPM refresh but at second 


V2.6.8.0
--------
 - PSPNM-462:  update to new TCP/IP stack version 2.1.19.0 
 - PSPNM-463:  firmware may write to DPM even if not allowed by handshake flags in case a device is no longer in data exchange 


V2.6.7.2
--------
 - PSPNM-460:  when DMA mode is active the values for status bitlists and IOPS may not always be correctly copied to DPM Input area 
 - PSPNM-461:  when DMA mode is active applications values for IOxS are not copied from DPM to IO-Devices 


V2.6.7.1
--------
 - PSPNM-457:  consumer IOPS in DPM stays "good" even if connection is broken 


V2.6.7.0
--------
 - PSPNM-261:  directly after connection establishment IO data 0 is transfered and is marked as valid (IOPS good) 
 - PSPNM-435:  feature: add support for user application to send DCP GET Requests 
 - PSPNM-438:  firmware shall check IP-addresses of IO-Devices inside database to reject database with invalid IP addresses 
 - PSPNM-440:  DCP Ident request is sometimes not sent to device when FastStartUp is enabled 
 - PSPNM-442:  inconsistent configuration packets are not detected leading to invalid content of data in DPM 
 - PSPNM-444:  Number of IOPS entries in Extended Status is not cleared with new configuration 
 - PSPNM-445:  packet configuration with duplicate ARUUID is accepted but should not 
 - PSPNM-446:  Ethernet Activity LED shall not be always on but shall blink if there is data exchanged 
 - PSPNM-447:  some GSDML datatypes are not supported by the swapping functionality of firmware 
 - PSPNM-449:  memory leakage if connection is lost and there is a not completely handled alarm pending 
 - PSPNM-452:  directly after connection establishment IOPS good is transfered to IO-Device even if user manually sets IOPS to bad in DPM 
 - PSPNM-454:  Get Switch statistics returns unexpected value for ulPortNum 
 - PSPNM-455:  feature: update to new rcX  v2.0.8.18 
 - PSPNM-456:  [loadable module]using loadable module on Channel unequal 0 will crash 


V2.6.6.0
--------
 - PSPNM-434:  get switch statistics does not work correctly when link state changes 
 - PSPNM-436:  DCP IdentifyResponses with unknown, padded blocks are ignored 


V2.6.5.0
--------
 - PSPNM-286:  feature: host application shall be able to read out to which nodes the IO-Controller is connected (neighbourhood information) 
 - PSPNM-328:  feature: host application shall be able to read the Ethernet Switch error counters 
 - PSPNM-423:  no parameters sent to submodules that report submodule state substitute during connection establishment 
